get_team_summary

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

The description implies it returns all agents ('todos los agentes'), but the schema includes an optional agent_id filter for a single agent, creating a mismatch. No disclosure of data freshness, pagination, or performance implications. Without annotations, the description carries the full burden and fails to clarify behavior.

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 line with a title-body structure (dash separated) and the query hint. No redundant words, but the inclusion of '[query]' is slightly unclear. Efficient for its length.

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 3 optional parameters, no output schema, and many sibling tools, the description is too sparse. It does not specify the structure of the summary, how filtering works, or what to expect in the response, leaving the agent with incomplete context.

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 descriptions cover 100% of parameters, so the baseline is 3. The description adds no additional meaning beyond the schema; it does not explain how filtering by agent_id affects the summary or how period and days are used together.

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 'Resumen del equipo — Vista general de todos los agentes con su carga de trabajo actual', clearly indicating it provides a team summary with agent workload. This distinguishes it from individual agent tools like get_agent_stats, though it could be more precise about verb+resource.

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 explicit guidance on when to use this tool versus alternatives. Siblings like get_agent_stats or get_agent_activity exist, but the description does not mention when to prefer this team overview over individual agent queries.

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