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

Annotations already declare readOnlyHint=false and destructiveHint=false. The description adds real value beyond them: it discloses the side effect (a file lands in .gluecron/specs/ with status ready and an autopilot picks it up) and a required 'repo' scope. It still says nothing about what is returned or what happens if a spec already exists.

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 sentences with no filler, but they are jargon-dense ('.gluecron/specs/', 'voice-to-pr.shipAsSpec', 'autopilot') and lead with internal mechanics rather than the user-facing purpose. Short, but not front-loaded on what the agent is accomplishing.

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 four-required-parameter mutation tool with no output schema and thin schema coverage, the description leaves key questions open: what the return value is, how owner/repo/title/body are used, and what happens on duplicate or invalid specs. The auth-scope note and side-effect disclosure help, but the definition is not complete enough to call it confidently.

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 25% – only 'body' is documented (as Markdown). The description never maps owner, repo, or title to their meaning, nor does it state that body is the spec content. With all four parameters required, this is a notable gap the description should compensate for but does not.

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 names an action ('Drop a spec file in .gluecron/specs/ with status: ready') and an internal wrapper ('Wraps voice-to-pr.shipAsSpec'), but it is framed in internal jargon rather than stating plainly that it creates a spec record for owner/repo with a title and body. It gestures at a sibling (voice-to-pr) without clarifying when to pick this tool instead.

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?

'Handle both voice + manual specs' and 'so the autopilot picks it up' hint at context, and the 'repo' scope requirement is a precondition. But there is no explicit when-to-use or when-not-to-use guidance relative to siblings like merjax_voice_to_pr or merjax_create_issue.

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