method

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered. The description adds the write-prerequisite (project name/id) which is useful operational context, but it never warns that 'delete' is irreversible or that destructive behavior is confined to that action, leaving a gap between the blanket destructiveHint and the actual four-action surface.

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 short sentences, purpose front-loaded before the action list and the write prerequisite. The formatting is slightly run-on (the action list collides with the 'Write:' clause), but nothing is padded or redundant.

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?

An 11-parameter, four-action dispatcher with no output schema and 18% schema coverage needs per-action parameter guidance and return-shape hints. The description supplies neither, so an agent cannot reliably tell which fields matter for which action.

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 only 18%, so the description carries the compensation burden and largely fails. It clarifies that 'project' accepts a name or id and is required for writes, but the other nine parameters (name, steps, category, method_id, project_id, description, code_example, related_component_id, model) are never explained, nor is it stated which parameters apply to which action.

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?

States a specific resource (project methods) and enumerates the supported verbs (create, list, update, delete), with a clarifying gloss of what a 'method' is (auth flows, deployment steps, patterns). It does not, however, distinguish this tool from siblings like create_component or rules, so an agent must infer the boundary.

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?

It gives one concrete precondition for writes (project="<name>" or project_id) but never says when to choose this tool over the many sibling CRUD tools, nor which action fits which situation. Usage is implied by the action list rather than stated.

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