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

The annotations already communicate read-only, idempotent, and non-destructive behavior, so the description does not need to restate that. The description adds useful context about the bundle contents and intended usage, but it does not add deeper behavioral caveats such as payload size, performance, or what happens when projectId is omitted.

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 sentences with no filler: the first sentence names the action and the complete payload, and the second gives usage timing. Information is front-loaded and each clause earns its place.

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 explains what the tool returns (the bundle components) even without an output schema, and it gives usage context. It does not explain edge cases like omitted projectId or empty projects, but those are partially addressed by the schema and annotations, leaving only minor gaps.

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 50%, with context and projectId well-documented in the schema. The description's mention of 'document summaries' and 'evidence summaries' indirectly relates to documentsLimit and evidenceLimit, but it does not explain the limits or their defaults; their names and min/max constraints carry most of the semantic weight.

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 action ('Load one project') and lists the exact components returned, which clearly identifies it as a context-bundle retrieval tool. It does not explicitly name a sibling alternative, but the component list is specific enough to distinguish it from report-producing and feasibility-analysis siblings.

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 provides concrete timing guidance: 'Use before composing reports or after scheduling analysis.' This gives an agent clear context for when to call the tool, though it does not mention when not to use it or name alternative tools.

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