privacy_security_get

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

Adds return object structure, state parameter effects (default, 404, 400), and a link to external spec. Annotations already indicate read-only, idempotent, non-destructive; description provides complementary detail without contradiction.

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 paragraphs: first states purpose, second details return and state. Efficient, no wasted words. Link to spec is helpful but could be integrated.

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?

With 2 params, no output schema, and annotations present, description provides return structure, state details, and external link. Sufficient for an agent to use correctly.

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 50% (productId lacks description). Description compensates by fully explaining state behavior (valid values, default, error responses). Does not elaborate on productId, but parameter name and type are self-explanatory.

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?

Clearly states 'Get privacy & security information for an app', specifies audience (enterprise procurement reviewers), and distinguishes from sibling tools like privacy_security_draft_delete and privacy_security_publish which are write operations.

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?

Mentions intended audience and state parameter behavior (live default, draft 404). Implicitly separates from write operations, but lacks explicit 'when not to use' or alternatives.

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