build_basecamp_pr_update

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose that this tool does NOT write to Basecamp (a key non-destructive behavior), which is valuable. However, it doesn't explain what it actually produces beyond 'Markdown,' whether it fetches the PR data from GitHub, what happens with the repo/pull_number, or whether auth/permissions are needed. The behavioral profile is only partially disclosed.

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 concise sentence with no wasted words. It front-loads the key verb and resource effectively. It's appropriately short, though it errs on the side of being too terse given the lack of supporting detail.

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?

The tool has 4 parameters (2 required), no annotation coverage at 0% schema description, and no description of output format despite having an output schema. The description does not explain what input data drives the Markdown generation, prerequisites, or how this relates to the sibling Basecamp-related workflow. For a tool that builds a document from PR data, this is under-specified.

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%, so the description must compensate — but it adds no parameter information whatsoever. The schema shows repo, owner, summary, and pull_number, but the description gives no hint of which are required, what summary is used for, how owner relates to repo, or what data pull_number selects. For a tool with zero schema coverage, this is a significant gap.

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 states the verb 'Build' and the resource 'Basecamp PR update,' and indicates it outputs Markdown without writing to Basecamp. However, it doesn't explicitly say it uses pull request data as the input source, and the phrase 'separate Basecamp MCP' is cryptic — it doesn't clarify what makes this distinct from other MCPs. It's clear enough about the general action but lacks specificity about what content the Markdown contains.

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 when-to-use guidance is provided. While the description implies it's a preview/dry-run variant (since it doesn't write to Basecamp), it doesn't name an alternative for the actual write operation, nor does it specify when to choose this over the many sibling tools. The 'without writing to Basecamp' clause hints at a dry-run use case but no explicit context is given.

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