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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so safety is covered. The description adds only the hint that queries are natural-language topics rather than exact names; it says nothing about matching semantics, ranking, result size, or the 62-item cap, which is a meaningful omission even at the lower annotation bar.

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?

Two short sentences with the useful example queries front-loaded and no padding; the only filler is the attribution/URL line, which is minor and harmless.

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 two-parameter search with no output schema, the definition covers the query intent adequately, but an agent still lacks any description of what a result contains and what `limit` does, so it is not fully self-sufficient.

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 0%, so the description must carry parameter meaning. The example strings do clarify what `query` accepts, but `limit` (integer, 1-62) is never mentioned anywhere, leaving half the parameters undocumented.

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?

"Search the Profullstack fleet" names a specific verb and resource, and the example queries ("podcast directory", "webhooks") show the tool matches services by topic. It is distinguishable from the list/get siblings in spirit but never says so explicitly.

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 examples imply free-text keyword search when you know roughly what service you want, but the description gives no explicit when-to-use versus when-not guidance and does not mention profullstack_fleet_list_services as the browse-everything alternative.

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