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

Annotations already mark the operation as read-only, so the description only needs to add behavior beyond that. It does so by disclosing that the result is 'full markdown,' which informs the agent about the response format and conversion behavior.

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 a single, well-structured sentence that front-loads the main behavior and packs essential parameter context into a parenthetical. There is no redundancy or 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 simple one-parameter read-only tool with an output schema and a clear identifier convention, the description covers everything needed to call it correctly. The mention of search provenance and the site-path format removes the main ambiguity.

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 provides only the parameter name and length constraints, so the description carries the full semantic burden. It clearly explains that id is a site path (e.g., /pricing) and that it comes from search results, making the parameter's meaning and expected format unambiguous.

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 the resource (a tabflows.com page) and the key identifier (a site path such as /pricing). It distinguishes the operation from search by requiring an id, though it does not explicitly differentiate from the sibling get_page tool.

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 gives clear context by specifying that the id is a site path 'as returned by search,' telling the agent where valid ids come from. It does not state exclusions or compare directly with get_page, but the provenance guidance is concrete and useful.

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