get_global_notice

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Read', which implies a non-mutating operation, but it does not disclose side effects, permissions, return format, or any other behavioral details. This is insufficient for a tool with zero annotation coverage.

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 short sentence that is efficiently worded and front-loaded. It states the essential purpose without any wasted words, making it highly concise and appropriately structured.

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?

The tool is low-complexity with one optional parameter and no output schema. The description states the purpose but does not indicate what the tool returns or any additional context. Since there is no output schema to compensate, a mention of the return value would improve completeness, but the simplicity of the tool makes a moderate score acceptable.

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 description does not mention the 'profile' parameter at all. However, the input schema covers it 100% with a descriptive line, so the baseline is 3. The description adds no additional semantic meaning beyond what the schema already provides.

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 clearly states the tool reads the global notice setting with a specific verb and resource. It distinguishes from sibling set_global_notice and clear_global_notice via the verb 'Read', though it does not explicitly name them. This is clear but could be more explicit about the contrast.

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 provides no guidance on when to use this tool versus alternatives. It does not mention that it is for viewing the current notice, nor does it reference set_global_notice or clear_global_notice as alternatives for modification. There is no context about when it should or should not be used.

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