mcp-github-project-manager

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers none. It doesn't mention that this is a mutation operation, what permissions are required, whether changes are reversible, what happens to unspecified fields, or any rate limits. The description fails to provide any behavioral context beyond the basic verb.

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 maximally concise with a single clear sentence. There's no wasted verbiage or unnecessary elaboration, though this conciseness comes at the cost of completeness. Every word earns its place in stating the basic operation.

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?

For a complex mutation tool with 6 parameters (including nested objects), 0% schema coverage, no annotations, and no output schema, the description is completely inadequate. It doesn't explain what an automation rule is, what fields can be updated, what the expected behavior is, or what the tool returns. The description fails to provide the necessary context for proper tool invocation.

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?

With 0% schema description coverage and 6 parameters (including complex nested objects for triggers and actions), the description provides zero information about parameters. It doesn't mention the required 'ruleId', the optional fields like 'name' or 'enabled', or the structure of triggers and actions arrays. The description fails to compensate for the complete lack of schema documentation.

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 'Update an existing automation rule' is a tautology that restates the tool name without adding specificity. It mentions the verb 'update' and resource 'automation rule' but doesn't distinguish what aspects can be updated or how this differs from other automation tools like 'enable_automation_rule' or 'disable_automation_rule'.

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 zero guidance on when to use this tool versus alternatives. There's no mention of prerequisites (like needing an existing rule ID), when this should be used instead of creating/deleting rules, or how it relates to sibling tools like 'create_automation_rule' or 'delete_automation_rule'.

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