Raw Freshsales API GET request

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

With no annotations, the description carries the transparency burden. It discloses the HTTP method (GET) and endpoint scope, which implies a read-only operation, but it does not mention authentication requirements, error behavior, or response format, leaving some behavioral ambiguity for a raw request tool.

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?

The description is only two sentences, front-loaded with purpose and examples, and contains no filler. Every word earns its place.

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 raw GET escape hatch, the description provides the base URL, path semantics, and usage guidance, which is largely sufficient. The lack of output schema and annotations is somewhat mitigated by the clear scope, though explicitly stating the return format would make it fully complete.

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?

The schema already covers both parameters fully, and the description adds value by specifying the base URL and giving example paths. This helps the agent understand how to construct the 'path' parameter beyond the schema's bare 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 identifies this as an escape hatch for any GET endpoint under the Freshsales API base URL not covered by other tools, with concrete examples like '/leads/filters'. This specific verb+resource+scope fully distinguishes it from the sibling tools.

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?

It explicitly states 'Only use when the other tools can't answer the question' and frames the tool as a fallback for endpoints not covered by other tools. This is excellent when-to-use guidance and names the alternative approach.

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