postforme_raw

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

Without annotations, the description carries full burden. It mentions handled auth/retries/rate-limiting but does not disclose potential destructive actions (e.g., DELETE) or error handling behavior. Some transparency, but gaps remain.

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?

Four sentences with no fluff. Front-loaded with main purpose. Each sentence adds necessary detail: when to use, how to specify path, optional components, and handled aspects. Highly concise.

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 API tool with no output schema, the description covers usage and constraints, but lacks mention of return value shape or error responses. The reference to docs partially compensates, but completeness could be higher.

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%, baseline is 3. Description adds value by emphasizing the requirement for full path including version segment, providing concrete examples, and clarifying optional params/body. This goes beyond schema.

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 the tool is an escape hatch to directly call any REST endpoint, specifying the verb 'call' and the resource as 'any Post for Me REST endpoint'. It effectively distinguishes from siblings by stating 'use this only when no dedicated tool exists'.

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 states when to use ('only when no dedicated tool exists') and that auth, retries, and rate-limiting are handled, providing clear guidance on context and alternatives.

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