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

Annotations declare readOnlyHint=true, and the description reinforces it by stating READ-ONLY and 'only GET is allowed', which is an enforceable constraint rather than a restatement. It also discloses the return format ('parsed JSON'). No error or rate-limit behavior is mentioned.

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?

Front-loads the tool's role, then the constraint, then the path format, then the return type in four tight sentences. The inline examples carry concrete information rather than 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 raw passthrough GET tool with one parameter and no output schema, the description covers purpose, constraint, input format, and return shape. An agent has everything needed to construct a correct call.

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 the path parameter documented, so the baseline is 3. The description adds real value beyond the schema by showing that the full path must include the query string and by demonstrating filter syntax such as 'StartDate~gte~2024-01-01' and 'sortby=-StartDate'.

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?

States a specific verb (GET) and resource (any Text-Em-All API path not wrapped by a dedicated tool) with explicit scope. The phrase 'escape hatch' plus 'not wrapped by a dedicated tool' cleanly separates it from every sibling like list_broadcasts or get_account.

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?

Gives a clear selection rule: use this only for paths that dedicated tools do not cover, and it flags the power-user audience. It does not name which dedicated tool to prefer for a given task, but the routing condition is unambiguous.

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