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

Annotations already declare readOnlyHint=true; the description reinforces and sharpens this by stating READ-ONLY and that only GET is permitted, which is a meaningful enforcement detail. It also discloses the return shape ('parsed JSON'). It omits auth requirements, error behavior, and rate limits, so it adds context without being exhaustive.

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 tight sentences, front-loaded with the escape-hatch framing and the read-only constraint, followed by the format rule and concrete examples. Every sentence earns its place; no filler.

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 raw passthrough with no output schema, the description covers the essential concerns: scope, HTTP method restriction, path format, and return type. Minor gaps remain around error responses and pagination semantics, though the query-string example partially covers the latter.

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%, so the baseline is 3, but the description adds real value beyond the schema by explaining that the full path must include the query string and by showing operator-style syntax ('StartDate~gte~2024-01-01'), which the schema example alone does not convey.

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 states a specific verb and resource ('GET any Text-Em-All API path') and frames the tool as a fallback for endpoints 'not wrapped by a dedicated tool,' which cleanly distinguishes it from every sibling (get_broadcast, list_broadcasts, etc.). An agent can tell instantly that this is the pass-through option for uncovered paths.

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 gives a clear selection condition — use it for paths the dedicated tools don't wrap — and states the hard constraint that only GET is allowed. It stops short of explicitly telling the agent to prefer a dedicated sibling when one exists, but that is strongly implied by 'not wrapped by a dedicated tool.'

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