Agent Status

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

Annotations only include title, so the description carries the full behavioral burden. It explicitly declares read-only status and no side effects, plus discloses JWT requirements and the graceful error-hint behavior when unauthenticated.

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?

Three tightly packed sentences with no filler. The primary purpose is front-loaded, alternatives are listed in one sentence, and the auth caveat is placed last without bloating the definition.

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?

All three parameters are documented in the schema, an output schema exists, and the description covers purpose, alternatives, read-only guarantees, and auth behavior. Nothing an agent needs to safely call this tool is missing.

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%, so the baseline is 3. The description adds value beyond the schema by explaining how parameters map to consolidated sections and that 'system' mirrors civitae_health, plus the auth caveat for 'me'.

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: a read-only dashboard combining agent profile, platform health, and governance state. Clearly distinguishes its consolidated scope from sibling tools by naming what it aggregates.

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?

Explicitly says when to use this tool (quick overview) and names specific alternatives for detailed needs: civitae_health, civitae_agents, and civitae_meetings. Also provides an auth prerequisite and expected failure behavior.

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