Team Collaboration Matrix

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds one genuinely useful non-annotation fact — the TEAM_DB_PATH dependency — but says nothing about cost, result size, or what the matrix contains beyond three noun phrases.

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?

A single front-loaded sentence that lists the three analytical outputs, followed by a short prerequisite clause. Nothing is wasted, though the telegraphic list style leaves the reader inferring relationships between the outputs.

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 output schema exists, so return values need not be described, and annotations cover safety. Still, for a four-parameter analytics tool with 25% schema coverage, the description leaves the agent guessing about period granularity, limit semantics, and when this analysis is preferable to sibling insight tools.

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 workspace_id is documented), so the description needs to carry the load and does not. It never explains what 'limit' limits (authors? pairs?), what values 'period' accepts beyond the default 'month', or what 'use_test_db' toggles.

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 verb and resource ('Analyze cross-author collaboration') and enumerates three concrete outputs: per-period activity heatmap, cross-linking patterns, and impact factor via inbound links. This is clearly distinct from generic siblings like team_get_statistics, though it never explicitly names or contrasts those siblings.

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?

There is no when-to-use guidance, no exclusions, and no routing to alternatives such as team_get_statistics or team_get_cross_project_insights. The only conditional statement is an environmental prerequisite ('Requires TEAM_DB_PATH'), which is a setup constraint rather than usage guidance.

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