get_project_manifest

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint. The description adds the important behavioral trait that no prior indexing is required, which is beyond the annotations. It does not contradict annotations. Some additional context about rate limits or side effects would be useful but not necessary given the safe profile.

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 two sentences, front-loaded with the main purpose, followed by return fields and a key note. Every sentence is necessary and no words are wasted. Highly concise and well-structured.

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 low complexity (2 parameters, no output schema), the description is complete. It lists the types of manifests parsed, the returned fields, and the important note about no indexing. No critical information is missing for this tool.

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 100%, so the description does not need to explain parameters. The description does not add meaning beyond the schema (e.g., how use_cache behaves). Baseline 3 is appropriate.

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 'Get parsed project metadata from package manifest files', listing specific manifest files and returned fields. It distinguishes itself from sibling tools by specifying its focus on manifest files and noting that no prior indexing is required. This is highly specific and leaves no 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 when to use (when needing manifest metadata) but does not explicitly state when not to use or provide alternatives. The note 'No prior indexing required' hints at differentiation from indexing-dependent tools, but there is no clear comparison with siblings.

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