peoplehub_list_week

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

No annotations are provided, so the description carries the full behavioral burden. The read-only nature is only implied by the verb 'Lista', and there is no mention of authentication/session requirements, data scope, pagination, or side effects. It does add useful context with the Monday-to-Sunday week boundary, but safety and dependency behavior are left to inference.

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 one short, efficient sentence that conveys purpose, week boundary, and default behavior. Every phrase earns its place, and the most important operational detail appears immediately.

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?

For a simple list operation with one optional parameter and no output schema, the description is nearly complete: it states what is listed, the week definition, and the default. It could be more complete by explicitly noting whether an active session is required and what the returned hour-load records look like.

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?

The schema already documents the single optional parameter's format and default value. The description adds value beyond the schema by clarifying that reference_date selects the week containing that date and that the week runs Monday through Sunday.

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 ('Lista'), a specific resource ('cargas de horas de una semana'), and scope ('lunes a domingo'). The resource is clearly distinct from sibling tools like peoplehub_list_activities, peoplehub_list_conceptos, and peoplehub_list_groups, so an agent can identify what this tool operates on without opening schemas.

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?

The description gives clear context about the default week selection (reference_date or today), but it never explicitly says when to choose this tool over alternatives such as peoplehub_list_activities or peoplehub_log_hours. Usage is implied by the purpose rather than clearly routed.

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