stripo_config

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds only 'READ-ONLY' and 'Makes no changes,' which duplicates the annotation. No additional behavioral details (e.g., pagination behavior, authentication, rate limits) are provided, falling short of enhancing transparency beyond structured signals.

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 concise (two sentences plus metadata). The READ-ONLY indicator and HTTP method are front-loaded. However, the structure could be improved by explicitly naming the resource or adding a brief example, but it remains efficient.

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 5 parameters, nested objects, and no output schema, the description provides minimal context. It confirms read-only and resource type but does not explain what 'Stripo config' contains, how pagination works, or the response format. Annotations help, but the description could be more complete for a tool with moderate complexity.

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 80% (4 of 5 parameters have in-schema descriptions). The description adds no parameter-specific information; it merely states the tool fetches config. Baseline score of 3 is appropriate since the schema does most of the documentation work.

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 clearly states the tool fetches Stripo config data and is read-only. The READ-ONLY emoji and 'Makes no changes' clarify the action. However, it does not explicitly differentiate from siblings like 'set_config' beyond the read-only hint, leaving slight ambiguity.

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 description implies usage for reading Stripo config without side effects, but lacks explicit when-to-use or when-not-to-use guidance. No alternative tools are mentioned, and the agent must infer from the read-only annotation that this is for retrieval only.

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