project.metadata_store

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

With no annotations provided, the description must disclose behavioral traits. 'Store' implies mutation, but it does not reveal key behaviors: whether it overwrites existing keys, persistence guarantees, size limits, or required permissions. This is a significant gap.

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, which is efficient but severely under-specified. It lacks structure such as separating usage notes, parameter details, or behavioral conditions. The brevity sacrifices clarity.

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 complexity of 3 required parameters, no annotations, no output schema, and over 100 sibling tools, the description is wholly inadequate. It does not explain return values, side effects, error conditions, or how this tool fits with siblings like 'project.metadata_query'.

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% and the description does not explain any of the three parameters (project_id, key, value). The tool's purpose is opaque without parameter context, and the description fails to add meaning beyond the raw schema field names.

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?

Description states 'Store project metadata.' It provides a verb and resource, but does not distinguish from sibling tools like 'metadata.store' or 'project.metadata_query'. The phrase is generic and does not clarify what 'store' entails (create/update/overwrite), making it 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 on when to use this tool versus alternatives such as 'metadata.store' or 'project.metadata_query'. The description offers no context about prerequisites, intended scenarios, or exclusion conditions.

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