describe_endpoint

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

No annotations are present, so the description carries the burden. It discloses that the tool is free, and describes the contents of the returned signature including price and response shape. It doesn't discuss side effects or auth, but for a metadata endpoint the key behaviors are covered.

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?

Two sentences, first gets directly to the point with 'Free' and the action, second provides usage guidance. No wasted words.

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?

For a one-parameter metadata tool, the description fully explains what the tool does, what information it returns, and when to call it relative to fetch_data. The absence of an output schema is acceptable because the tool's purpose is to describe that shape.

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 coverage is 100% with a clear example for the only parameter 'path'. The description only says 'one endpoint' and doesn't add extra semantics beyond the schema, so baseline 3 is appropriate.

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?

Description states a specific action ('Show the full call signature') on a specific resource ('one endpoint'), enumerating what is included: required/optional parameters, allowed values, price, and response shape. It clearly differentiates from siblings by focusing on metadata rather than data fetching or searching.

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?

Explicitly tells the agent when to use it: 'Call this before fetch_data if you are unsure about parameters.' This names fetch_data as the alternative and gives a clear condition, satisfying the when/alternative requirement.

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