fmp_describe

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

No annotations are provided, so the description carries the full burden. It states it's a discovery tool returning documentation, implying safe read-only behavior, but does not explicitly mention no side effects, speed, or access requirements. Slightly more detail would enhance transparency.

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?

Three short, front-loaded sentences with no fluff. Each sentence adds value: purpose, role as discovery tool, and usage tip.

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?

Given the output schema exists, return values need not be explained. The description fully covers purpose, usage, and context for a simple documentation tool. It is complete and self-sufficient.

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% for the single endpoint parameter, and the description adds examples like 'income_statement', 'historical_price_adjusted', which clarify naming conventions beyond the schema's generic description.

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?

The description clearly states it 'Get detailed documentation for an FMP endpoint' and positions it as a discovery tool. It distinguishes from sibling tools like fmp_fetch (which fetches data) and fmp_list_endpoints (which lists endpoints).

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 advises 'Use this before calling fmp_fetch to know required vs optional params', providing clear when-to-use guidance. The sibling tool list further aids decision-making.

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