analyze_attachment_resource

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

With no annotations, the description carries the full burden of behavioral disclosure. It indicates a read operation but says nothing about side effects, required permissions, failure modes, or return values. The adapter availability qualifier hints at a prerequisite but does not explain actual behavior.

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 a single sentence with no fluff, front-loaded with the verb and resource. It is efficient in structure, though the brevity sacrifices necessary content. As a structure score, it earns credit for being concise and well-organized.

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 description is severely inadequate for a tool with five parameters, no output schema, and no annotations. It does not explain what the tool does with the resource, how parameters affect behavior, or what the output will be. The conditional about adapter availability adds little context.

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 description coverage is 0%, so the description must compensate for the lack of parameter documentation. It does not mention any of the five parameters (resource_uri, max_queries, max_keywords, section_hint, assignment_requirements). The phrase 'client-provided MCP resource' weakly maps to resource_uri, but this is far from sufficient.

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 states a specific verb ('Read') and resource ('client-provided MCP resource'), but it omits the analysis aspect implied by the tool name and instead focuses on a conditional prerequisite (adapter availability). It does not clearly differentiate from sibling tools, though none seem to read attachment resources. The purpose is understandable but vague.

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 alternatives. The only condition mentioned is 'when a standards-compliant resource adapter is available', which is a prerequisite rather than a usage guideline. No exclusions or alternative tool references are provided.

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