persons.get

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. Fails to disclose error behavior (404 vs 403), authentication requirements, or what data the 'person' contains. 'Get' implies read-only but lacks confirmation of idempotency or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise single sentence with no filler. Front-loaded with verb and resource. However, breverity crosses into under-specification given lack of supporting annotations and schema descriptions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Inadequate for a 2-parameter required tool with no output schema. Missing accountId context crucial for multi-tenant APIs. Fails to clarify relationship between 'persons' and 'customers' resources present in sibling tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage. Description mentions 'by id' which maps to personId, providing minimal semantic value. Completely omits accountId despite it being a required scoping parameter, leaving critical parameter unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States specific action (Get), resource (Ryft person), and lookup method (by id). Distinguishes from sibling persons.list via 'by id' implying single-record retrieval. However, 'Ryft person' is domain jargon not explained, and relationship to sibling customers.get is unclear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this vs persons.list or customers.get. The 'by id' phrase implies usage when a specific ID is known, but fails to address the accountId requirement or prerequisites for valid invocation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.