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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable behavior beyond those: it returns content regardless of status (pending, approved, denied, snoozed) and instructs that after a native Connect approve, the agent should poll status and must not open a new authorize tab from this read. No contradiction with annotations.

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 dense but well-structured: core purpose first, then the canonical use case, then a workflow caveat, then routing. Every sentence carries useful information, though the auth-flow sentence adds a bit of complexity for an otherwise simple read tool.

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?

With no output schema, the description clearly communicates what the tool returns (full description, deliverable content, context payload) and that all statuses are covered. The required parameters are documented in the schema. It could mention error or permission edge cases, but for a single-item read with strong annotations this is sufficiently complete.

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 100%; item_id and companyId are already fully documented in the schema. The main description adds no additional parameter-level semantics, so the baseline of 3 applies.

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 uses a specific verb+resource+scope: 'Read ONE Command Center card by id' and details exactly what is returned (full description, full deliverable content, full context payload) in ANY status. It clearly distinguishes itself from the plural sibling get_command_center_items and from knowledge files.

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?

Explicit routing guidance is provided: 'THE tool for retrieving what an already-decided card actually said' and a dedicated Routing line ('Need an already-decided card's full content ... use this, not knowledge files'). It also gives workflow-specific advice about polling status after a Connect approve rather than opening a new authorize tab.

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