apply_expose

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

Discloses key behaviors: convergent (idempotent), tables dark by default, revocation of dropped items. No annotations provided, so description carries full burden and meets it well.

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?

Well-structured with clear front-loading of action. Each sentence adds value, though slightly verbose. No redundant content.

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?

Covers manifest structure, convergence, and default behavior. Lacks explanation of return values, error conditions, or success/failure outcomes. Adequate for a mutation tool but could be more complete given 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 description coverage is 100%, so baseline is 3. Description summarizes manifest structure but does not add new parameter syntax or format details beyond the schema.

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?

Clearly states the verb 'apply' and the resource 'declarative authorization manifest to a project', includes the HTTP endpoint. Distinguishes from sibling tools like 'validate_manifest' (validation) and 'get_expose' (retrieval) by focusing on application.

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?

Implies usage for applying manifests but does not explicitly mention alternatives or when not to use. The convergence note ('applying twice is a no-op') provides guidance but no direct comparison to sibling tools.

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