Library Profile Usage

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

With no annotations provided, the description must disclose behavioral traits. It merely says 'summarize', implying a read-only operation, but lacks details on side effects, auth needs, rate limits, or output format. The description does not add sufficient context beyond the tool name.

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 extremely short (4 words) but at the expense of clarity. It is under-specified rather than concise. Every sentence should earn its place, but here the single sentence provides minimal utility.

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 the tool has 11 parameters, no output schema, and many sibling tools, the description grossly lacks detail. It does not explain the scope of 'usage', filtering options, pagination (via cursor/page/limit), or the meaning of the 'detail' and 'groupBy' parameters. Completely insufficient for an agent to use effectively.

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 description provides no information about the 11 parameters in the input schema. Schema description coverage is 0%, so the description bears full responsibility, yet it adds zero value regarding parameter meaning or usage.

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 'Summarize quality profile usage' provides a verb ('summarize') and a resource ('quality profile usage'), but it is vague. It does not specify what 'usage' means or distinguish it from the sibling tool 'quality_profile_usage'.

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 guidance is given on when to use this tool versus the many sibling tools related to quality profiles, such as 'quality_profile_usage', 'update_quality_profile', or 'clone_quality_profile'. No alternatives or exclusions are mentioned.

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