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

Annotations already declare readOnly, idempotent, non-destructive behaviour, so the safety profile is covered. The description adds that the listing is public and sourced from affix-io.com/tools, which is useful remote-fetch context. It says nothing about response size, freshness, or whether the catalogue is cached, so it adds only modest value over the annotations.

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?

One sentence, zero waste, with the resource front-loaded before the purpose clause. Nothing is padded or restated.

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 discovery tool with no output schema, the agent still does not know what the listing returns (names? IDs? descriptions? schemas?) or how to act on it. Annotations cover safety and the source URL is stated, but the return shape and the query semantics remain unaddressed.

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?

There is a single optional `query` object and schema coverage is 100%, so the baseline is 3. The description adds no meaning about what query keys are accepted or how they filter the listing, leaving the free-form `additionalProperties` bag entirely unexplained.

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 and resource: 'List the public AffixIO tools from affix-io.com/tools.' An agent can tell this is a catalogue/discovery operation. It does not, however, differentiate itself from the obvious siblings tools_search and tools_detail, which is what a 5 would require.

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 clear usage context: consult it 'so a Medusa agent can choose the right capability before acting,' i.e. a pre-action discovery step. It names no exclusions and never routes the agent to tools_search or tools_detail for narrower lookups, so it stops short of a 5.

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