rec_profile_list

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds only the word 'Saved' plus output fields that the output schema already provides. It discloses no ordering, pagination, or auth behavior beyond the safety profile.

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 short, front-loaded phrase with no filler, though it is a sentence fragment rather than a complete action statement. It is appropriately sized for a simple zero-param listing tool.

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?

The output schema covers return fields and annotations cover read-only safety, so the description need not explain results. However, it never states the operation or how it differs from adjacent profile tools, which is a meaningful gap for selection.

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 tool takes zero parameters, so there is nothing for the description to clarify; per the rubric this yields a baseline of 4. The parenthetical field list refers to returned data, not inputs.

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 the resource ('Saved capture profiles') and the returned fields, but uses a noun phrase with no verb, so it never explicitly says it lists them. An agent can infer the action from the tool name and siblings, but the description itself does not distinguish 'list' from 'get' or 'save'.

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?

No when-to-use guidance, prerequisites, or alternatives are given. It does not mention rec_profile_get, rec_profile_save, or rec_profile_delete, leaving the agent to infer that this is the unfiltered list operation.

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