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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only mentions the HTTP method and capacity for larger requests, but does not state whether it is read-only, any side effects, authentication requirements, or rate limits. This is insufficient for a network operation.

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 concise at three sentences and front-loaded with the core purpose. The added group and billing info are tangential but brief. No unnecessary repetition occurs.

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 there is no output schema, the description should at least mention what the search returns and how pagination or cursors work. It only vaguely references 'larger requests' and 'large cursors' without explaining response format or usage. For a search tool with one parameter, this is incomplete.

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?

With 0% schema description coverage, the description must compensate for the single parameter 'searchTerm'. It merely says 'provide a search term', adding no semantic value beyond the schema's type string. It does not explain formatting, encoding, operators, or length limits, leaving the agent underinformed.

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 searches all of Twitter with a search term, and differentiates it from the GET sibling by noting it's a POST request for larger requests. The title 'Search for large cursors' is a bit ambiguous, but the description clarifies the purpose. It does not confuse with other search 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?

The description implies use when you need 'larger requests' compared to GET, providing some usage context. However, it does not explicitly mention when not to use the GET alternative or any conditions for choosing POST. It also mentions billing and group, which are not usage guidance.

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